Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

完成对things-i-wish-i-knew-before-i-wrote-my-first-android-app.md的翻译 #56

Closed
wants to merge 5 commits into from

Conversation

bobmayuze
Copy link
Member

This translation is done by Bob.Ma with help from 西二旗剑客

This translation is done by Bob.Ma with help from 西二旗剑客
@bobmayuze bobmayuze changed the title Translation 完成对things-i-wish-i-knew-before-i-wrote-my-first-android-app.md的翻译 Dec 26, 2015
@Glowin Glowin mentioned this pull request Dec 27, 2015
@@ -7,21 +7,21 @@



我的第一个应用写的非常弱。事实上,它已经弱到让我把它从应用商店直接下架了来抹去在我简历上到污点。 如果在我开发它之前我对开发有Android开发有任何了解就不会做的那么弱了吧。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

terrible 建议翻译成“糟糕”

来抹去在我简历上的污点。

如果在我开发它之前对Android开发有些了解就不会做的那么糟糕了吧。

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

它已经烂到我把它从应用商店下架,并且都不想在简历上列出它

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

如果在我开发它之前开发有Android开发有任何了解就不会做的那么弱了吧。

@xiuweikang
Copy link
Contributor

说实话,翻译的有点烂。

@bobmayuze
Copy link
Member Author

- -有错误请指出= =我会改进的!

[![Screen Shot 2015-07-09 at 4.25.00 PM](http://i2.wp.com/www.philosophicalhacker.com/wp-content/uploads/2015/07/Screen-Shot-2015-07-09-at-4.25.00-PM.png?resize=620%2C435)](http://i2.wp.com/www.philosophicalhacker.com/wp-content/uploads/2015/07/Screen-Shot-2015-07-09-at-4.25.00-PM.png)

## 5\. Learn from other people who are smarter and more experienced than you.
## 5\. 从那些大神地方学习
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

跟那些比你聪明和有经验的大神学习

@Glowin
Copy link
Member

Glowin commented Dec 30, 2015

@xiuweikang 欢迎给 @bobmayuze 提意见 👍

@xiuweikang
Copy link
Contributor

@lihb 他都提到了。我审核完了 @bobmayuze 你可以根据我们的提议改下。

@lihb
Copy link
Contributor

lihb commented Dec 30, 2015

我这边也审核完了,你修改下先吧。

@bobmayuze
Copy link
Member Author

Got it.

@linb@xiuweikang 两位前辈的指导下修改了一些翻译上的错误
感谢指出!
@lihb
Copy link
Contributor

lihb commented Dec 30, 2015

@bobmayuze “安利”是什么意思?求教。

@bobmayuze
Copy link
Member Author

@lihb 安利的话最开始是一个品牌 最早的微商 旨在通过人们对于健康的高度追求来出售自己的产品 安利的早期营销策略是- -给你洗脑,说这个产品怎么怎么好。。。现在已经可以当动词用了
比如说我觉得github是个很棒的网站 于是我就把它安利给我的同学 也就是推荐,拉他一起

@lihb
Copy link
Contributor

lihb commented Dec 31, 2015

@bobmayuze ,原来如此,哈哈,涨姿势了,谢啦。


When you’re writing an app you’re going to make mistakes. Other people have already made those mistakes. Learn from those people. You’re wasting your time if you repeat the avoidable mistakes of others. I wasted a ton of time on my first app making mistakes that I could have avoided if I just spent a little more time learning from experienced software developers.
读下[Pragmatic Programmer](http://www.amazon.com/The-Pragmatic-Programmer-Journeyman-Master/dp/020161622X). Then read [Effective Java](http://www.amazon.com/Effective-Java-Edition-Joshua-Bloch/dp/0321356683)这本书吧 然后去读下[Effective Java](http://www.amazon.com/Effective-Java-Edition-Joshua-Bloch/dp/0321356683)这本书。 这两本书可以帮你避免一些新手常犯的错误。即使在你看完这两本书之后,也请保持着新手的姿态向大神们学习。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then read 没有翻译哦。

@lihb 前辈的指导下修改了小问题
@linb 我这用stackedit.io 试过了,OK的呀
@Glowin Glowin closed this Feb 19, 2016
@Glowin
Copy link
Member

Glowin commented Feb 19, 2016

因为文章翻译重复了,我就 close 这个 PR 了哈,谢谢 Bob 的翻译。

@Glowin Glowin reopened this Feb 19, 2016
@Glowin Glowin closed this Feb 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants